Icon

EPIC on FHIR (Patient Dashboard)

There has been no title set for this workflow's metadata.

Epic on FHIR Demo Dashboard

This dashboard visualizes data of patient from the sandbox environment.

To learn more about this workflow, please read: https://www.knime.com/blog/interact-epic-on-fhir-web-services

URL: EPIC on FHIR https://fhir.epic.com/

This workflow is a sample dashboard of Patient which exists in the Sandbox data. In order to proceed please provide a Bearer Token and the FHIR patientid.For this example this workflow consumes 4 EPIC on FHIR services which are Read only. 1) First one calls Patient data.2) Followed by it, Diagnosis of Patient is returned by calling Web Service for "Condition" of user.3) Once the Diagnosis is retuned, Medication Requests for the same user is carried out.4) FInally, Future Goals of Patients are queried using web service for "Goals".Towards the end, all results are visualized in a consolidated component of Tile Views in "View" component.Please note that token creation and refresh mechanism should be handled at provider's end, when this is done, a "Get Request" can be use to get thetoken and Patient ID and it can be overriden in "Token and Patient ID" component to create a complete workflow. Include complete token along with"Bearer "Add FHIR ID ofpatient View Token andPatient ID Patient Details Diagnosis Medication Future Goal This workflow is a sample dashboard of Patient which exists in the Sandbox data. In order to proceed please provide a Bearer Token and the FHIR patientid.For this example this workflow consumes 4 EPIC on FHIR services which are Read only. 1) First one calls Patient data.2) Followed by it, Diagnosis of Patient is returned by calling Web Service for "Condition" of user.3) Once the Diagnosis is retuned, Medication Requests for the same user is carried out.4) FInally, Future Goals of Patients are queried using web service for "Goals".Towards the end, all results are visualized in a consolidated component of Tile Views in "View" component.Please note that token creation and refresh mechanism should be handled at provider's end, when this is done, a "Get Request" can be use to get thetoken and Patient ID and it can be overriden in "Token and Patient ID" component to create a complete workflow. Include complete token along with"Bearer "Add FHIR ID ofpatientView Token andPatient ID Patient Details Diagnosis Medication Future Goal

Nodes

Extensions

Links

Download

To use this workflow in KNIME, download it from the below URL and open it in KNIME:

Download Workflow
Created by: franziska
Created at: 2021-12-15
On NodePit since: 2022-04-29
Last update: 2024-11-14
Created with KNIME version: v5.1.2
Tags: EPICFHIRHL7HealthCareEHRSmartAppDigital Healthcare

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!